What & Why

In AgentFlow v2, when a single Condition output is connected to two or more nodes (parallel branches), selecting a different branch still executes one of the nodes wired to the unselected branch.

Root cause

determineNodesToIgnore in packages/server/src/utils/buildAgentflow.ts uses edges.find() to locate the edge for each unfulfilled condition output:

for (const index of unfulfilledIndexes) {
    const ignoreEdge = edges.find((edge) => edge.source === nodeId && edge.sourceHandle === `${nodeId}-output-${index}`)
    if (ignoreEdge) {
        ignoreNodeIds.push(ignoreEdge.target)
    }
}

find() returns only the first matching edge. When one output (-output-${index}) fans out to multiple targets, only the first target is added to ignoreNodeIds. Downstream, child nodes are executed unless they are in that list (if (ignoreNodeIds.includes(childId)) continue), so the remaining parallel targets are never gated and leak into other branches.

Because the leaked node depends on edge ordering, the same bug also surfaces as the opposite symptom (a matched branch appearing to "stop"), which matches the reports in the linked issues.

Reproduction

• Start → Condition
• Condition output-0 → LLM A and LLM B (two edges on the same output)
• Condition output-1 → LLM C

Expected: selecting output-1 runs only LLM C.
Actual: LLM C and one of LLM A / LLM B both run.

Minimal flow JSON used to reproduce:

Bug Test Agents.json

🎥 Before (bug) — selecting output-1 wrongly runs an output-0 node too:

Fix

Use edges.filter() and ignore every target connected to an unfulfilled output:

for (const index of unfulfilledIndexes) {
    const ignoreEdges = edges.filter(
        (edge) => edge.source === nodeId && edge.sourceHandle === `${nodeId}-output-${index}`
    )
    for (const ignoreEdge of ignoreEdges) {
        ignoreNodeIds.push(ignoreEdge.target)
    }
}

🎥 After (fixed) — selecting output-1 runs only the correct node:

Related issues

• [BUG] Agentflows v2 Condition not works when 2 or more condition connects same node #4660 — Agentflows v2 Condition not works when 2 or more condition connects same node
• Flow execution stops at Condition node when multiple branches converge into single LLM node #5501 — Flow execution stops at Condition node when multiple branches converge into single LLM node
• Condition and Human Input nodes stall when their output connects to an input that already has a value/connection #5358 — Condition / Human Input nodes stall when output connects to an input that already has a value/connection

Notes

• Scope limited to the AgentFlow v2 condition routing. A similar find() pattern exists in the legacy v1 IfElse path (packages/server/src/utils/index.ts), but it involves a different node type / routing model and is intentionally left out of this PR.